If your laptop’s CPU is running very hot and you’ve tried to undervolt it, you’ve probably discovered there’s no easy way to do so—especially on laptops whose BIOS doesn’t expose those controls. I ran into the same issue with my Ryzen 7 5800H, despite numerous attempts, I couldn’t undervolt because the firmware simply wouldn’t allow it. While it may seem drastic, disabling Turbo Boost is one workaround—and you might be surprised how little real-world performance you lose by turning it off.
Discover gists
| ----- | |
| ## name: fable-economy | |
| description: > | |
| Token optimization protocol for Claude Fable and other high-capability / high-cost models. | |
| Apply this skill at the START of any session involving iterative code builds, multi-file | |
| projects, design systems, game development, document generation, or any task likely to | |
| span more than 3 exchanges. Trigger phrases: “let’s build”, “add these features”, | |
| “improve this”, “refactor”, “implement all of”, “make it look better”, or any request | |
| that implies multiple changes to an existing artifact. Also trigger when the user asks |
EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.
I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.
Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.
Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca
This guide walks you through the process of connecting to a Bluetooth device on a Linux system using the bluetoothctl command-line tool. It covers initial setup, scanning, pairing, and connecting procedures, along with troubleshooting tips.
- A Linux distribution with Bluetooth support (e.g., Arch Linux).
- The
bluezpackage installed, which providesbluetoothctland related utilities. - A working Bluetooth adapter installed on your system.
- Sudo privileges to execute commands that require root access.
| #!/usr/bin/env bash | |
| # Atomic Arch / atomic-lockfile AUR campaign check | |
| # Sources: | |
| # - https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/FGXPCB3ZVCJIV7FX323SBAX2JHYB7ZS4/ | |
| # - https://www.sonatype.com/blog/atomic-arch-npm-campaign-adds-malicious-dependency | |
| # - https://ioctl.fail/preliminary-analysis-of-aur-malware/ | |
| set -uo pipefail | |
| # Known IOC strings: the malicious npm dep names this campaign rotates through, | |
| # plus the payload's path inside the npm package ("preinstall": "./src/hooks/deps"). |
A reference guide for implementers building on the AI agent verification stack
Co-authored by:
- Vincent Wu — ERC-8263 (Onchain Proof Layer for AI Agents)
- Damon Zwicker — Observation Commitment Protocol (OCP)
- Tiago Merlini — ERC-8004 / WYRIWE / execution-attestation profile
| ## CRONTAB HINTS AND TIPS | |
| ## | |
| ## | |
| ## Entry Description Equivalent To | |
| ## @yearly (or @annually) Run once a year at midnight in the morning of January 1 0 0 1 1 * | |
| ## @monthly Run once a month at midnight in the morning of the first of the month 0 0 1 * * | |
| ## @weekly Run once a week at midnight in the morning of Sunday 0 0 * * 0 | |
| ## @daily Run once a day at midnight 0 0 * * * | |
| ## @hourly Run once an hour at the beginning of the hour 0 * * * * | |
| ## @reboot Run at startup @reboot |
Some notes/resources for bypassing anti-bot/scraping features on Cloudflare, Akamai, etc.
Очередная инструкция на случай амнезии.
YT-DLP - БАЗИРОВАННАЯ тулза для скачивания контента с медиахостингов, и многие проги ей завидуют хранят под капотом именно её ядро. Оседлав этого жеребца, смотришь на других наездников, как на бедолаг с раздолбанным очком. Приступим.
yt-dlpработает в связке сffmpeg, поэтому скачиваем свежие релизы первого и второго и распаковываем исполняемые файлы в одну папку.
- Поскольку yt-dlp работает через CLI, чтобы вызывать его из любого места добавим путь к программе в переменную среды Windows
PATH.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
